<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso-iso-8859-1">
<LINK REL="Start" HREF="index.html">
<LINK REL="Contents" HREF="toc.html">
<LINK REL="Prev" HREF="483Themecolorsforpies.html">
<LINK REL="Next" HREF="51Enablingthecachesystem.html">
<STYLE TYPE="text/css"><!--
BODY { font-family: serif }
H1 { font-family: sans-serif }
H2 { font-family: sans-serif }
H3 { font-family: sans-serif }
H4 { font-family: sans-serif }
H5 { font-family: sans-serif }
H6 { font-family: sans-serif }
SUB { font-size: smaller }
SUP { font-size: smaller }
PRE { font-family: monospace }
A { text-decoration: none }
--></STYLE>
</HEAD>
<BODY>
<A HREF="toc.html">Contents</A>
<A HREF="483Themecolorsforpies.html">Previous</A>
<A HREF="51Enablingthecachesystem.html">Next</A>
<HR NOSHADE>
<H1><A NAME="5">5 Understanding the JpGraph caching system</A></H1>
<P> To reduce load on the web server JpGraph implements an advanced
 caching system which avoids the burden of always having to run the full
 image script.</P>
<P> Depending on the complexity of the image script (for example if it
 is doing several DB lookups) this could significantly improve
 performance.</P>
<P> The rationale behind this is of course performance, and the
 observation that very few graphs are really real-time, i.e. needs to be
 updated absolutely every time the graphing script is called.</P>
<P></P>
<HR NOSHADE>
<A HREF="toc.html">Contents</A>
<A HREF="483Themecolorsforpies.html">Previous</A>
<A HREF="51Enablingthecachesystem.html">Next</A>
</BODY>
</HTML>
